The Oracle Linux operating system must audit all uses of the chmod syscall.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-221782	OL07-00-030410	SV-221782r603260_rule		Medium

Description
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033

Description

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033

STIG	Date
Oracle Linux 7 Security Technical Implementation Guide	2021-06-14

Details

Check Text ( C-36299r602491_chk )
Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chmod" syscall occur. Check the file system rules in "/etc/audit/audit.rules" with the following command: # grep -iw chmod /etc/audit/audit.rules -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod If both the "b32" and "b64" audit rules are not defined for the "chmod" syscall, this is a finding.

Check Text ( C-36299r602491_chk )

Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chmod" syscall occur.

Check the file system rules in "/etc/audit/audit.rules" with the following command:

# grep -iw chmod /etc/audit/audit.rules

-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod

-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod

If both the "b32" and "b64" audit rules are not defined for the "chmod" syscall, this is a finding.

Fix Text (F-36263r602492_fix)
Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chmod" syscall occur. Add or update the following rule in "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod The audit daemon must be restarted for the changes to take effect.

Fix Text (F-36263r602492_fix)

Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chmod" syscall occur.

Add or update the following rule in "/etc/audit/rules.d/audit.rules":

-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod

-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -k perm_mod

The audit daemon must be restarted for the changes to take effect.